We're mostly all OK for compatibility with WordPress 5.3, the only exceptions are some display issues with Twenty Twenty. The content area is more narrow, and the markup is slightly different. This updates the schedule display to use alignwide styles if there are more than two tracks (otherwise it breaks out of the space), and now looks for and uses the theme's template for the Day of Event page. The offline page still looks wonky, but we can address that with #205.

Other core changes to note:

The media improvements seem to be mostly around resizing images or hooking into the upload process, so our uploads are good (we use the media library directly). There’s no change to wp_unique_filename, so obscuring the filenames should continue to work.

Things we should watch for:

• Any "mismatched function signature" PHP warnings in logs – WP 5.3: Introducing the spread operator
• Any TypeError JS errors – WordPress 5.3: Backbone Upgrade Guide
• We should maybe update the cron hooks to use time() instead of current_time( ‘timestamp’ ), but the latter should continue to work – Date/Time component improvements in WordPress 5.3

An enhancement we could make: any meta fields exposed by the API can now define a schema in the register_post_meta call. We don't seem to need this anywhere ATM, but useful to know about. WP 5.3 Supports Object and Array Meta Types in the REST API

To test

To test these changes specifically:

• Make sure a page with a schedule still looks OK
• Check that the Day of Event template works

Otherwise, checking out the 5.3 branch in mu/ while you're working from now on would be a good way to test 👍